Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update clause_7_name_assignment_policy.adoc #127

Merged
merged 1 commit into from
Jul 28, 2021
Merged

Conversation

ghobona
Copy link
Contributor

@ghobona ghobona commented Jul 2, 2021

Two edits made:

  • changes objectType to definitionType, so as to be consistent with the Naming Rule section
  • add a section describing support for Content Negotiation

Two edits made:

* changes objectType to definitionType, so as to be consistent with the Naming Rule section
* add a section describing support for Content Negotiation
@ghobona
Copy link
Contributor Author

ghobona commented Jul 2, 2021

This Pull Request addresses Issue #107

The use of Content Negotiation is consistent with the approach taken by Web APIs, OGC APIs in particular.

Cc: @rob-metalinkage @RogerLott

Copy link

@chris-little chris-little left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems sensible and consistent if we support content negotiation

@ghobona ghobona merged commit 1e49706 into master Jul 28, 2021
@ghobona ghobona deleted the fix_for_issue_107 branch July 28, 2021 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants